Invalid workspace configuration for Yarn 4.x — pipeline is failing.

The workspaces key is not a recognized configuration setting in Yarn 4.10.3 (as indicated by the pipeline failure). In Yarn v2+, workspaces are defined in package.json, not .yarnrc.yml.

After confirming the correct syntax, move the workspace configuration from .yarnrc.yml to package.json. For reference, the pipeline error was:

[error] 1-1: Usage Error: Unrecognized or legacy configuration settings found: workspaces. Run 'yarn config' to see the list of settings supported in Yarn. Command 'yarn install' failed with exit code 1.

🌐 Web query:

How to configure Yarn v4 workspaces in package.json?

💡 Result:

Short answer — in Yarn v4 you declare workspaces in the root package.json with a workspaces field (glob patterns), make the root private, optionally set packageManager, and use the workspace: protocol in workspace-to-workspace dependencies. Example:

Root package.json
{
"private": true,
"packageManager": "[email protected]",
"workspaces": [
"packages/",
"apps/"
]
}

Workspace package (packages/pkg-a/package.json)
{
"name": "@myorg/pkg-a",
"version": "1.0.0",
"main": "dist/index.js",
"dependencies": {
"lodash": "^4.17.21"
}
}

Workspace package that depends on another workspace (packages/pkg-b/package.json)
{
"name": "@myorg/pkg-b",
"version": "1.0.0",
"dependencies": {
"@myorg/pkg-a": "workspace:*"
}
}

Notes:

• workspaces can be an array of glob patterns (root manifest). [1]
• Use "workspace:*", "workspace:^", etc. to reference local workspace versions and keep resolution consistent. You can still run yarn workspaces foreach, yarn workspace , and use yarn workspaces focus to limit installs. [1][2][3]

References:
[1] Yarn manifest (package.json) — workspaces docs.
[2] Yarn workspaces feature page.
[3] Yarn protocols (workspace: protocol examples).